Account management systems and methods

ABSTRACT

A method of managing accounts relating to presentation instruments includes receiving at a host computer system information from a client defining an account management rule. The rule includes an event, a condition, and an action to be taken if the condition is satisfied upon the occurrence of the event. The method also includes monitoring a plurality of accounts for the occurrence of the event, upon the occurrence of the event for a specific account, evaluating the condition, based on the evaluation, taking the action, thereby managing the account without human intervention, and providing notification of the action to an individual.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation-in-part of, and claims the benefit of, U.S. application Ser. No. 10/982,526, filed Nov. 5, 2004, (Attorney Docket No. 020375-054700US), entitled “ACCOUNT MANAGEMENT SYSTEMS AND METHOD,” which application is entirely incorporated herein by reference for all purposes. This application is related to co-pending, commonly assigned U.S. patent application Ser. No. 10/271,875 (Attorney Docket No. 020375-025200US), entitled, “RULES MANAGEMENT SYSTEMS AND METHODS,” filed on Oct. 15, 2002, which application is entirely incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

The present invention relates generally to credit card processing services. The present invention relates more specifically to automated post-issuance presentation account management systems and methods.

The birth of a credit card generally begins with an applicant supplying information to complete a credit card application provided by an issuer. The issuer is usually a financial institution that issues the credit card and extends credit to the cardholder through the credit account linked to the credit card. Typically, the process of supplying the necessary information can be done electronically or by paper. The credit card application is then processed, and if approval criteria are met, a credit card is issued to the applicant who now becomes a cardholder. The process of issuing a credit card involves a number of steps including, for example, coding the credit card with cardholder data on the magnetic stripe and embossing the cardholder's name, account number and expiration date on the credit card.

When the credit card is first received by the cardholder, the cardholder needs to activate the credit card. Activation of the credit card is generally done by requiring the cardholder to call the issuer from his/her home phone. Once the credit card is activated, the cardholder may then use the credit card to make purchases or conduct transactions.

A typical credit card transaction involves a number of parties. In addition to the cardholder and the issuer, the parties involved in a credit card transaction include a merchant, an acquirer and a credit card association such as Visa or MasterCard. The acquirer is a business entity, e.g., a commercial bank, that has a business relationship with the merchant and handles credit card transactions from that merchant.

A typical credit card transaction involves the following steps. First, the merchant calculates the amount of the transaction or purchase and seeks payment from the cardholders The cardholder then presents the merchant with his/her credit card. The merchant then runs the credit card through a point of sale terminal. The point of sale terminal captures credit card and sales information and sends such information together with an authorization request to the acquirer. The acquirer, in turn, processes the information received from the point of sale terminal and forwards any relevant information and the authorization request to the issuer. The issuer processes the relevant information and the authorization request to determine whether the transaction should be authorized. The issuer then sends an approval or denial code back to the acquirer. The acquirer relays the approval or denial code to the point of sale terminal for use by the merchant. If the transaction is authorized, the cardholder is allowed to consummate the transaction with the merchant. Typically, at a later time, the accounts maintained by the issuer and the acquirer are settled and reconciled. The end result is that the issuer transfers the transaction amount minus a fee to the acquirer. The acquirer then deducts a fee from the amount received from the issuer. The remaining amount is then transferred by the acquirer to the merchant's account.

While certain parties, such as the issuer and the acquirer, are described above as performing certain functions, in typical situations, most or all of the functions to be performed by these parties may be performed on their behalf by third parties. For example, in some instances the third party may be a credit card processing organization. The credit card processing organization may provide credit card processing services on behalf of many clients, such as banks, or other financial institutions, and the like, who wish to issue credit accounts to their customers. The credit card processing organization may receive and process credit card applications, issue credit cards, receive user account information relating to a transaction, approve and process the transaction information, and provide payment to the merchant. Periodically, the credit card processing organization produces financial statements that summarize transactions for customers and bill the customers at least a minimum amount based upon their usage of the credit account. One example of a credit card processing organization is First Data Corporation, Greenwood Village, Colo.

Post-issuance account management can be a labor intensive process. Any number of circumstances—over-limit charges, address changes, irregular usage patterns, sustained usage in good standing, and the like—may trigger the need for an individual to become involved in the management of an account. This is costly to the processing organization and/or the issuer. Thus, systems and methods are needed which reduce or eliminate the need for human involvement in the account management process.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention thus provide a method of managing accounts relating to presentation instruments. The method includes receiving at a host computer system information from a client defining an account management rule. The rule includes an event, a condition, and an action to be taken if the condition is satisfied upon the occurrence of the event. The method also includes monitoring a plurality of accounts for the occurrence of the event, upon the occurrence of the event for a specific account, evaluating the condition, based on the evaluation, taking the action, thereby managing the account without human intervention, and providing notification of the action to an individual.

In some embodiments, receiving information identifying a condition includes receiving a logical expression using at least one element. The at least one element may be derived from one or more account attributes. The one or more account attributes may include an activity flag, account creation data, credit balance, and/or rewards program balance. The event may include a daily account cycle, account creation, usage of the presentation instrument, and annual fee posting date. The action may result in a change to an account attribute. The account management rule may be selected from a library of account management rules.

In other embodiments, a method of managing bankcard accounts includes receiving at a host computer system a selection of an account management rule from a library of account management rules. The account management rules may include information defining an event, a condition relating to at least one element associated with bankcard accounts, and information defining an action to be taken based on the condition upon the occurrence of the event. The method also includes storing the selection at the host computer system, collecting bankcard data, and processing the bankcard data using the account management rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition.

In still other embodiments, a computer-readable medium has computer-executable instructions for performing a method. The method includes receiving information from a client defining an account management rule. The rule includes an event, a condition, and an action to be taken if the condition is satisfied upon the occurrence of the event. The method also includes monitoring a plurality of accounts for the occurrence of the event, upon the occurrence of the event for a specific account, evaluating the condition, based on the evaluation, taking the action, thereby managing the account without human intervention, and providing notification of the action to an individual. The computer-executable instructions also may include instructions for collecting bankcard transaction data and processing the bankcard transaction data using the account management rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. Receiving information identifying a condition may include receiving a logical expression using at least one element. The at least one element may be derived from one or more account attributes.

In further embodiments, a system for managing bankcard accounts includes a processor, a storage device, and an output device. The processor is configured to receive from a client information defining an event, receive information identifying a condition relating to at least one element associated with bankcard accounts, receive information defining an action to be taken based on the condition upon the occurrence of the event, and store the event, the condition, and the action as an account management rule. The processor may be further configured to collect bankcard transaction data and process the bankcard transaction data using the account management rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. The information identifying a condition may include a logical expression using at least one element. The at least one element may be derived from one or more account attributes. The one or more account attributes may include an activity flag, account creation data, credit balance, and/or rewards program balance. The event may include a daily account cycle, account creation, usage of the presentation instrument, and annual fee posting date. The action may result in a change to an account attribute. The account management rule may be selected from a library of account management rules.

Other embodiments provide a method of providing bankcard services. The method includes receiving at a host computer system information from a client defining an event, receiving at the host computer system information identifying a condition relating to at least one element associated with bankcard accounts, receiving at the host computer system information defining an action to be taken based on the condition upon the occurrence of the event, and storing the event, the condition, and the action as a business rule at the host computer system. The method may include collecting bankcard transaction data, and processing the bankcard transaction data using the business rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. The method also may include collecting bankcard account data, and processing the bankcard account data using the business rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. The operation of receiving information identifying a condition may include receiving a logical expression using the at least one element. The at least one element may be derived from one or more account attributes. The one or more account attributes may be selected from a group consisting of state of residence, base interest rate, current, previous, and last balance, delinquency, client-defined fields, payment history, and promotional information. The event may be selected from a group consisting of statement processing, new processing day, monetary posting, non-monetary posting, monetary adjustment, specified day, account transfer, and account creation. The action may be selected from a group consisting of set a fee value, send a letter, calculate a finance charge, calculate average daily balance, waive fees, increase or decrease fees, reinstate an item, allocate and distribute payments across monetary fields, satisfy minimum payment due, process pay ahead, accumulate monetary information, update a masterfile field, call another rule, assign or remove an identifier, set account limits or thresholds, insert information into a statement, print a message, generate a plastic, and change a credit line. The action may result in a change to an account attribute. The business rule may be selected from a library of business rules. The method also may include collecting bankcard data and running a simulation of the business rule using the bankcard data such that upon the occurrence of the event, information identifying the action is written to a file with respect to bankcard accounts that satisfy the condition.

In other embodiments, a method of providing bankcard services includes receiving at a host computer system a selection of a business rule from a library of business rules. The business rules may include information defining an event, a condition relating to at least one element associated with bankcard accounts, and information defining an action to be taken based on the condition upon the occurrence of the event. The method also may include storing the selection at the host computer system, collecting bankcard data, and processing the bankcard data using the business rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition.

In still other embodiments, a method of providing bankcard services includes receiving at a host computer system a selection of a business rule from a library of business rules. The business rules may include information defining an event, a condition relating to at least one element associated with bankcard accounts, and information defining an action to be taken based on the condition upon the occurrence of the event. The method also may include storing the selection at the host computer system, collecting bankcard data, and running a simulation of the business rule using the data such that upon the occurrence of the event, information identifying the action is written to a file with respect to bankcard accounts that satisfy the condition.

In yet other embodiments, a computer-readable medium having computer-executable instructions for performing a method includes receiving from a client information defining an event, receiving information identifying a condition relating to at least one element associated with bankcard accounts, receiving information defining an action to be taken based on the condition upon the occurrence of the event, and storing the event, the condition, and the action as a business rule. The method also may include collecting bankcard transaction data, and processing the bankcard transaction data using the business rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. The method also may include collecting bankcard account data, and processing the bankcard account data using the business rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. The operation of receiving information identifying a condition may include receiving a logical expression using the at least one element. The at least one element may be derived from one or more account attributes. The one or more account attributes may be selected from a group consisting of state of residence, base interest rate, current, previous, and last balance, delinquency, client-defined fields, payment history, and promotional information. The event may be selected from a group consisting of statement processing, new processing day, monetary posting, non-monetary posting, monetary adjustment, specified day, account transfer, and account creation. The action may be selected from a group consisting of set a fee value, send a letter, calculate a finance charge, calculate average daily balance, waive fees, increase or decrease fees, reinstate an item, allocate and distribute payments across monetary fields, satisfy minimum payment due, process pay ahead, accumulate monetary information, update a masterfile field, call another rule, assign or remove an identifier, set account limits or thresholds, insert information into a statement, print a message, generate a plastic, and change a credit line. The action may result in a change to an account attribute. The business rule may be selected from a library of business rules. The method also may include collecting bankcard data, and running a simulation of the business rule using the bankcard data such that upon the occurrence of the event, information identifying the action is written to a file with respect to bankcard accounts that satisfy the condition.

In other embodiments, a system for providing bankcard services includes a processor, a storage device, and an output device. The processor may be configured to receive from a client information defining an event, receive information identifying a condition relating to at least one element associated with bankcard accounts, receive information defining an action to be taken based on the condition upon the occurrence of the event, and store the event, the condition, and the action as a business rule. The processor may be further configured to collect bankcard transaction data, and process the bankcard transaction data using the business rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. The processor also may be configured to collect bankcard account data, and process the bankcard account data using the business rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition. The information identifying a condition may include a logical expression using the at least one element. The at least one element may be derived from one or more account attributes. The one or more account attributes may be selected from a group consisting of state of residence, base interest rate, current, previous, and last balance, delinquency, client-defined fields, payment history, and promotional information. The event may be selected from a group consisting of statement processing, new processing day, monetary posting, non-monetary posting, monetary adjustment, specified day, account transfer, and account creation. The action may be selected from a group consisting of set a fee value, send a letter, calculate a finance charge, calculate average daily balance, waive fees, increase or decrease fees, reinstate an item, allocate and distribute payments across monetary fields, satisfy minimum payment due, process pay ahead, accumulate monetary information, update a masterfile field, call another rule, assign or remove an identifier, set account limits or thresholds, insert information into a statement, print a message, generate a plastic, and change a credit line. The action may result in a change to an account attribute. The business rule may be selected from a library of business rules. The processor also may be configured to collect bankcard data, and run a simulation of the business rule using the bankcard data such that upon the occurrence of the event, information identifying the action is written to a file with respect to bankcard accounts that satisfy the condition.

In other embodiments, a method of providing bankcard services includes receiving from a client an if-then statement that includes information defining an event, storing the if-then statement as a business rule. The if portion of the statement may include a condition relating to at least one element associated with bankcard accounts, and the then portion of the statement may define an action to be taken based on the condition upon the occurrence of the event.

Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the present invention may be realized by reference to the remaining portions of the specification and the drawings wherein like reference numerals are used throughout the several drawings to refer to similar components.

FIG. 1 illustrates a first screen display in a rules management system according to the present invention.

FIG. 2 is a system for managing rules according to the present invention.

FIG. 3 illustrates a second screen display in a rules management system according to the present invention.

FIG. 4 is a credit card program that may be implemented using the system of FIG. 2.

FIG. 5 is a processing environment according to embodiments of the present invention.

FIG. 6 is a point-in-time processing environment according to embodiments of the present invention.

FIG. 7 is a simulation environment according to embodiments of the present invention.

FIGS. 8A and 8B are first and second simulation screen displays, respectively, that may result from the simulation environment of FIG. 7.

FIG. 9 illustrates a first exemplary method of managing presentation instrument accounts according to embodiments of the invention, which method may be implemented in the system of FIG. 2.

FIG. 10 illustrates a second exemplary method of managing presentation instrument accounts according to embodiments of the invention, which method may be implemented in the system of FIG. 2.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the present invention provide systems and methods for post-issuance presentation instrument account management. Many credit card accounts are administered by credit card processing companies. Herein, such processing companies are referred to as credit card processing organizations or simply processing organizations. Processing organizations administer credit card accounts on behalf of banks, retailers, financial institutions, and other business that wish to issue credit cards according to guidelines established by such businesses. Herein, such businesses are referred to as clients, as in clients of the processing organization. Credit card account owners are referred to herein as account owners or customers, as in customers of the clients of the processing organizations. Finally, herein “merchants” refers to a business that accepts credit cards as payment for merchandise or services.

Processing organizations desire to reduce the human involvement needed to manage active accounts. These entities also desire to provide their clients greater control over the management of such accounts. According to embodiments of the present invention, clients and/or processing organizations may establish rules by which accounts are to be managed. Embodiments also provide tool for designing and implementing these rules in a processing environment such that the rules may be used to manage the accounts without requiring intervention by a customer service representative or other individual. Such systems and methods also may be used to design and implement credit card programs as will be described with respect to FIG. 1.

FIG. 1 illustrates a first screen display 100 in a system for managing rules in a credit card processing environment. The system architecture will be explained in more detail hereinafter; however, the screen display 100 illustrates a number of important aspects of the present invention. A client of a credit card processing organization might encounter the display screen 100 while designing a credit card program for its customers. As will be explained, the client may interface with the system using a computer connected to a network, such as the Internet. A software application resident on the client's computer may generate the user interface through which the client interacts with the rules management system. The application may be a standard web browser. Alternatively, the application may be a custom application that generates a user interface having windows such as the screen display 100. Many other examples are possible and apparent to those having skill in the art.

Through the user interface, the client may select or design “rules” that define the credit card program the client wishes to offer its customers. A rule is a conditional statement based on variables within the credit card processing environment. In one embodiment, the conditional statements are “If-Then” statements that produce an “action” when the conditional statement is satisfied. In a navigation pane 102, the screen display 100 includes a list of available rules in the late fee calculation area. A first list 104 includes the conditional portion of the rule, and a second list 106 includes the actions that may be taken when the condition is satisfied. Actions may include set a fee value, send a letter, calculate a finance charge, calculate average daily balance, waive fees, increase or decrease fees, reinstate an item, allocate and distribute payments across monetary fields, satisfy minimum payment due, process pay ahead, accumulate monetary information, update a masterfile field, call another rule, assign or remove an identifier, set account limits or thresholds, insert information into a statement, print a message, generate a plastic, change a credit line, and the like. A work area 108 provides additional definition of the rule.

The variables upon which the rules operate are “account attributes” and “elements.” For example, an account attribute may include the state in which a customer resides. This is an important account attribute because the laws in the customer's state may dictate certain bounds within which the client's program operates, such as the maximum interest rate the client may apply to its customers' account balances. Other account attributes may include state of residence, base interest rate, current, previous, and last balance, delinquency, client-defined fields, payment history, promotional information, and the like. Rules may also operate on elements, which are combinations of account attributes. For example, “minimum payment due” may be an element that is a combination of a “minimum payment due percentage” and the customer's account balance. Many other elements are used in the rules management system. Rules also may include “formulas” based on account attributes, elements, and other variables.

In some cases, an Action also may be subsequent decision criteria. For example, the decision criteria Method Override can also be an action. A Method Override is an optional setting that represents a set of pricing parameters, which can be associated to an account. The initial value of a Method Override can be used as decision criteria and then set to a new value as the result of an action. Any subsequent decisions would then use the new value in their decision process, rather than beginning of the process value. The client has the option to use the beginning of the process value or the iterative value.

In the example illustrated in FIG. 1, as shown in the work area 108, the selected rule “$10.00 fee no waiver” relates to billing a late fee. In this rule, the conditional statement is based on the attribute “number of cycles delinquent,” the element “accumulated credit amount,” and the formula “late fee formula.” The conditional statement is satisfied, or true, when “accumulated credit amount” is greater than “late fee formula” and “number of cycles delinquent” is greater than 2. The conditional operators in the formula, shown in the column 110, may include > (greater than), < (less than), = (equal to), >= (greater than or equal to), <= (less than or equal to), <> (not equal to), / (not), and the like. Other conditional operators are possible. The conditional conjugates in the formula, shown in the column 112, may include AND, OR, NOT, and the like. The action “Bill $10.00” appears in the action field 114. In this example, when the conditional statement is true, $10 is added to the customer's account balance. Thus, a rule may result in a change to an account attribute or element, as in this example, wherein the rule changes the account balance attribute.

Rules are designed to be evaluated upon the occurrence of “events.” In the present example, the event, “statement processing” triggers evaluation of the “$10.00 fee no waiver” rule. Other events might include, new processing day, monetary posting, non-monetary posting, monetary adjustment, specified day, account transfer, account creation, account anniversary, and the like. Thus, upon the occurrence of an event, rules triggered by the event are evaluated, and, if satisfied, result in the action associated with the rule. This combination of event-rule-action may be referred to herein as a “business rule.”

As will be explained further below, prior to processing rules, the account and transaction data upon which the rules operate may be “segmented.” Segmentation may occur based on particular account attributes, elements, and the like.

In some embodiments, clients may define events and segmentation rules. Such client-defined events and segmentations may be proprietary to the client and remain unavailable to other clients of the processor, thereby enabling a client to differentiate itself in the credit card market while using the same processor as other issuers. A client-defined event may be, for example, a collection of external, client-defined attributes, transmitted in a suitable electronic storage arrangement, for the purpose of creating a unique entry point for a decision process. The client would define rules that would use the client-defined attributes in combination with bankcard attributes. An example of a client-defined event is the transmission of file, containing accounts and a suggested pricing structure for those accounts. The client-defined event would evaluate the suggested pricing structure in combination with that account's current Method Override value and other bankcard attributes, in order to make a determination to activate the suggested pricing structure with an action.

Client-defined segmentation is the classification of client-defined attributes into separate and distinct logical groups for the purpose of associating an identifier to that account denoting its classification and/or for creating different processes for decisions. The client would build a segmentation rule where the action is an assignment of this classification, which may in turn dictate the next logical rule in the decision process or be used later for other bankcard activity. An example is creating one segmentation rule that evaluates a client-defined suggested pricing structure and based on the value, will perform an action to assign an identifier. This identifier is then used to dictate which of five available rules to process. Each of these five rules evaluate a different set of bankcard attributes, in order to make a determination to activate the suggested pricing structure with an action.

A collection of rules that define a credit card program constitute a “policy.” Thus, according to the present invention, a credit card processing organizations may provide its clients with a user interface through which the client may select or design rules that form a policy detailing the credit card program the client will offer its customers. Account and transaction data relating to customers of the client are then processed by the credit processing organization according to the policy. The process will be explained in more detail hereinafter.

Referring now to FIG. 2, one example of a system 200 for managing rules in a credit card processing environment will be described. The system 200 is merely one of many possible embodiments of a system according to the present invention. Those skilled in the art will recognize many different equivalent configurations within the scope of the present invention. Thus, this example of the present invention is not to be considered limiting. The system 200 includes a rules database 202, an account attribute database 203, an application server 204, and a web server 206. The rules database 202, the account attribute database 203, the application server 204, and the web server 206 may be separate elements of the system 200, as shown, or the components may reside together within a single computing device. In some embodiments, the rules database 202, the account attribute database 203, the application server 204, and the web server 206 are collocated within a single facility, while in other embodiments the components are distributed geographically and in communication either directly, as shown, or through a network 208, also shown.

The rules database 202 and the account attribute database 203 each may be any suitable computing device that includes an electronic storage arrangement. Suitable computing devices include personal computers, work stations, mainframes, servers, and the like. Suitable electronic storage arrangements include magnetic storage media, such as tape or disk drive systems, optical storage media, such as CD ROM and DVD, and solid state storage systems, such as RAM. The rules database 202 and the account attribute database 203 each may be configured with software that provides for the storage and retrieval of electronic information. The software may be well-known, commercially available software, such as Microsoft Access, SQL, DataBase II, Oracle, and the like, or the software may be custom-designed software.

The application server 204 also may be any suitable computing device, such as a mainframe computer, a workstation, a server, a personal computer, and the like. The application server 204 may include a large capacity storage system, such as those described above with reference to the rules database 202 and the account attribute database 203. Alternatively or additionally, the application server 204 may rely on the rules database 202, the account attribute database 203, and/or other storage environment for large capacity storage requirements. Other examples are possible.

The web server 206 also may be any suitable computing device, such as a mainframe computer, a workstation, a server, a personal computer, and the like. The web server 206 also may include suitable electronic storage, such as described above with reference to the rules database 202. The web server 206 may be configured with software that provides an electronic interface, via the network 208, for external clients or internal users of the rules management system 200. In some embodiments, the web server 206 includes software that provides a security/authentication function that ensures clients attempting to access the rules management system 200 are valid clients. Some embodiments of the web server 206 also include software that monitors client software being used to access the rules management system 200 and provides the opportunity to update the software as necessary.

The network 208 may be any suitable electronic network. For example, the network may be the Internet, a local area network, a wide area network, an Ethernet, a virtual private network, and the like. Through the network 208, clients may access the system 200 via a client computer 210. The client computer 210 may be any suitable computing device such as a mainframe computer, a workstation, a server, a personal computer, and the like. The client computer 210 may be configured with software, such as web browser software, that allows the client computer 210 to access the web server 206, and other parts of the rules management system 200. Alternatively, the client computer 210 may be configured with custom application software designed specifically for operation with the rules management system 200. As mentioned above with respect to the web server 206, the web server 206 may include software that monitors the custom application software on the client computer 210 and provides updates as necessary. Other examples are possible.

The system 200 also includes a transaction database 212 that may be any of the suitable computing and/or storage arrangements discussed previously. The transaction database 212 collects and stores transaction records that originate with merchants. For example, when a merchant accepts a credit card as payment for goods or services, the merchant generates a transaction record and transmits the transaction record to the merchant's bank. The merchant may use devices such as the telephone transaction arrangement 214, the terminal transaction arrangement 216, and the like, to transmit transaction records. Although shown as merely a database connected to the network 208, the transaction database 212 may be a collection of databases and systems that collect and distribute transaction records. For example, as mentioned above, the merchant may transmit the transaction record to the merchant's bank, which in turn transmits it to the appropriate credit card organization, such as Visa or MasterCard. The credit card organization may then transmit the transaction record to the processing organization that processes transactions on behalf of the client that issued the credit card used in the transaction that resulted in the transaction record. According to this embodiment of the present invention, the transaction database 212 represents a storage medium that stores transaction records to be processed according to the rules within the rules management system 200.

Attention is now directed to FIG. 3, which illustrates a second screen display 300 in a system for managing rules in a credit card processing environment. A client may encounter such a screen display when designing a credit card program according to the present invention. A rules tree window 302 logically groups the business rules that constitute a credit card program using known symbology. In brief, the higher branches of the tree are represented by the least-indented lines. The more indented the line, the further down the tree hierarchy the item. A plus (+) or minus (−) sign preceding an item indicates whether the branch is collapsed or expanded, respectively. Selecting a line in the tree causes detailed information relating to the line to be displayed in the work area 304.

Under a “policies” branch 308 of the rules tree, rules are organized first by events, then by segments, then by business rules. Thus, in this example, two events are listed: statement cycle and transaction posting (although in this example, no rules are listed under transaction posting, the header “Transaction Posting” is available). Under the branch heading “Event: Cycle” 310 of the tree, a number of segment rules appear. The two higher level segment rules are “Premier” and “Default.” Thus, upon processing data for a statement cycle (the event that triggers execution of rules in the “Cycle” branch of the tree), data is first segmented according to the “Premier” and “Default” rules. Processing will be explained in more detail hereinafter. The logic behind this grouping of rules will be clearer in light of the following example with reference to FIG. 4.

FIG. 4 illustrates a hypothetical credit card program 400 to be offered by Bank ABC, a client of a processing organization using the present invention. In this hypothetical example, Bank ABC currently offers a “Standard Market” credit card program having the attributes listed in the standard market window 402. The attributes include an annual fee of $25, a late fee of $15, and an interest rate of “Prime+9%.” Bank ABC wishes to design a new credit card program within its existing program. The new program will have several “levels” for different of ABC's customers. The “Premier Program,” having the attributes listed in the premier program window 404, will form the basis of the plan. Within the Premier Program, three subprograms will be offered: Vandemark, Elite, and Distinction. The subprograms will have the additional or alternative attributes listed in the subprogram windows V, E, D, respectively. The attributes of the Premier, Vandemark, Elite, and Distinction programs determine how credit card data will be processed for customers in each of the programs. Thus, when designing the program using the present invention, ABC Bank will organize the business rules according to the program levels.

Attention is now directed to FIG. 3 in combination with FIG. 4. As stated previously, business rules listed under the event “Cycle” perform segmentation of customer data according to the program within which the customer falls. One of the attributes in each customer's data file will relate to the customer's credit card program. Thus, the first segment rule “Premier” causes the business rules that fall under it in the tree hierarchy to operate on data relating to customers in the Premier program. Other data may be processed according to the rules under the “Default” segmentation rule branch of the tree. Within the Premier branch of the tree, customer data may be further segmented for processing according to the Elite, Vandemark, and Distinction segmentation rules. The plus sign (+) in front of each of these segmentation rules indicates that the associated branch is displayed in collapsed view, while the minus sign (−) in front of the Premier segmentation rule, and more particularly in front of the “General Premier Pricing” group, indicates that the business rules associated with the Premier program are displayed in the expanded view. A group allows a user to define sets of processing area rules that the user would like associated with an event or a segmentation action. This simplifies set up for new marketing programs and ensures consistency across portfolio processing.

Under the General Premier Pricing group branch of the tree, several business rules are listed that would be used to generate actions during statement processing (the event) if the conditions in the rule are satisfied. One of these business rules “$10 fee no waiver” will be explained further below.

FIG. 3 also illustrates several branches outside the Policy branch in the tree hierarchy. These include: Segmentation Rules, Processing Area Rules, Action Sets, and Formulas. Each is shown in the collapsed view. These branches may be considered libraries of rules, actions, and formulas from which clients can select the building block of their policies. Thus, clients may select predesigned business rules, modify rules in the library, or create their own rules. For example, the “$10 fee No Waiver” rule may be a predesigned rule in the library, which the client can include in a policy as is, or modify, as will be explained. An icon, such as the rule builder icon 310 may be used to initiate the construction of a rule from scratch, in which case the client has the flexibility to complete all the data fields in the work area 108 discussed in more detail below.

Attention is redirected to FIG. 1 for a discussion of the rule building process. As discussed previously, FIG. 1 illustrates a screen display 100 a client might encounter while creating or selecting rules that define a policy, or credit card program. The rules listed in the navigation pane 102 are a portion of the Processing Area Rules branch of the tree hierarchy discussed above with reference to FIG. 3. This is indicated by the navigation line 116 of the navigation pane 102. Continuing with the hypothetical example discussed above, the screen display 100 depicts what a client might see while designing a rule relating to late fee calculations in the Premier program. By entering information into the various fields in the work area 108, the client is able to customize a rule that determines the method by which a customer's late fee is calculated. The building blocks of the rule may be selected from various branches in the tree hierarchy. Once the rule is constructed, it can be incorporated into the tree by selecting the “Apply” icon 118. Then, as discussed above with reference to FIG. 3, the rule may be referenced under a policy, as was the case with the “$10 fee no waiver” rule under the policy designed by ABC Bank. The policy may be stored at the rules database 202 of FIG. 2 for later use in the processing environment.

In addition to the hierarchy of rules discussed thus far, some embodiments provide for the selection and creation of policy-wide rules that are not necessarily event-triggered. These rules may, for example, evaluate all actions prior to execution and alter the action under certain circumstances. For example, suppose a particular processing event results in two, seemingly contradictory actions. In the first action, a business rule has determined that a customer has been actively using a credit card account for more than one year, which, according to the rule, entitles the customer to a reduction in interest rate of 1% for his loyalty. However, in the second action, a different business rule has determined that the same customer has been late in paying his bill for each of the last two months. A “global” rule may be created by the client or selected from the library that compares all actions being taken with respect to a particular account and corrects any actions that contradict other actions. In this case, the global rule may prevent the late-paying customer from receiving the interest rate reduction. Many other examples of global rules are possible, and this example is not to be considered limiting.

The foregoing discussion represents but one example of a process for creating, selecting, displaying, and organizing rules according to the present invention. Many other examples are possible and apparent to those having skill in the art. For example, some embodiments of the present invention may use a series of nested folders to display and represent the hierarchical relationship of rules within a policy. Other embodiments may represent the rules as tables in a relational database, macros in a spread sheet, or any combination of the foregoing. Thus, this example of the present invention is not to be considered limiting.

Having described the process for creating rules according to the present invention, attention is now directed to FIG. 5 for a discussion of the process by which the rules are used to process customer account and transaction data according to the present invention. FIG. 5 illustrates a processing environment 500, which includes a more detailed view of a portion of the system 200 described with respect to FIG. 2. As can be seen, the processing environment 500 includes a user interface 502 (which is analogous to the client computer 210 of FIG. 2), the web server 206, the application server 204, the rules database 202, and the account attribute database 203. Additionally, the processing environment 500 includes a processing area 504 within which the rules operate on customer account and transaction data. The processing environment 500 may reside within the application server 204, or any other suitable computing environment. The processing environment 500 represents a batch process.

The batch process depicted in FIG. 5 may be executed upon the occurrence of a particular event. For example, on the day for generating statements, a batch process may be executed to produce statements for each customer. In another example, at the end of a period of time, such as a day, accumulated transactions may be processed for posting to customers' accounts. In some embodiments, the batch process is not related to any particular event but is executed periodically to process data relating to any event that has occurred in the preceding period. The processing environment 500 includes an ETL process 506 (Extract, Transform, and Load) wherein rules are removed (extracted) from the rules database 202 and converted (transformed) from the format in which the rules are stored on the rules database 202 into the format in which the rules are used for processing data. The rules are then placed (loaded) into the processing area 504 of the processing environment 500. The rules may be stored, for example in DB2 (DataBase II) code, and converted into VSAM (Virtual Storage Access Method) code for processing. Other processing techniques also may be used.

The processing area 504 includes a number of processing engines: an inference engine 510, a segmentation engine 511, an action engine 512, a get element engine 514, a put engine 516, an allocation engine 517, and a formula engine 518. Each engine is designed for a particular function relating to the processing of customer account and transaction data according to the rules. The inference engine 510 resolves the conditional portion of rules relating to customer account and transaction data. The segmentation engine matches customer account and transaction data to the appropriate client policy and the appropriate segment within the policy. For example, the data being processed by the processing organization in a given batch is not necessarily limited to a single client. Thus, the data must be matched to the appropriate client and then to the appropriate credit card program of the client. The action engine 512 manages the process of resolving the action portion of the business rules. It cooperates with the put engine 516 which actually accomplishes the updating of any account attributes affected by the process. The get element engine 514 extracts elements and attributes used in the processing of customer account and transaction data. The allocation engine 517 resolves issues relating to the allocation of payments received from customers. For example, if a customer has balances in different categories (e.g., subject to different interest rates), then the allocation engine 517 may be used to determine to which balance categories a payment should be posted. The formula engine 518 resolves any formulas used in the conditional portion of the rules.

The processing engines each include a data access layer 519 that provides an interface to each engine and the data being processed. For example, the data access layer 519 of the interface engine 510 may pull transaction data from the transaction database 212 (FIG. 2), customer account data from the account attribute database 203, and the like. Other examples are possible.

The processing environment 500 also includes an audit function 520. The audit function 520 monitors extractions, updates, and other functions relating to the rules database 202 and generates an audit report 522. For example, in some embodiments, the audit function 520 produces a report of all rules added to the database, and all rules rolled into and out of production during a period of time and associates them with particular batch processes and/or job numbers.

The processing environment 500 also includes a performance measurement function 524. The performance measurement function 524 receives data relating to various metrics from the processing area 504 and generates a performance measurement report 526 that may be used to monitor the efficiency and operability of the system. For example, in some embodiments, the performance measurement function 524 reports on all account attributes changed during a particular batch process.

In some embodiments, the processing environment includes a Rules I/O engine 550. The Rules I/O engine 550 allows rules to control file accesses. It performs a number of functions, including, for example, “Open File as Input,” “Open File as Output,” “Close File,” “Read Next,” and the like. Additionally, however, the Rules I/O engine 550 allows information to be written to files during rules processing. Hence, when an action includes “Writing” to one or more files, the information can be written to the files without waiting until rules processing concludes, thereby improving the process.

In some embodiments, the processing environment allows for information to be shared across multiple Events via Account Level Criteria 552. Account Level Criteria include variables, counters, and the like, through which information is passed from one event to another. Account level criteria may be numeric or non-numeric values. Hence, one Event can set an Account Level Criteria which may be subsequently used as the basis of decision-making by one or more other Events. For example, the result of a decision is an action to change a bankcard attribute of status. Since status is used in other events for that same account, when status is changed, the Account Level Criteria can be set to “Frozen Status”. Other events would then evaluate the Account Level Criteria for “Frozen Status” as part of that event's decision rule.

Attention is directed to FIG. 6 which illustrates a “point-in-time” processing environment 600. In addition to operating in batch mode, the rules management system may operate upon demand in a point-in-time processing mode. The “point-in-time” processing environment 600 includes the rules database 202, a point-in-time processing area 602, and several subsystems. These include a letters subsystem 604, an embossing subsystem 606, and a statement subsystem 608. Other embodiments include other subsystems. The letters subsystem 604 may generate correspondence to card holders, merchants, clients, and other entities. The embossing subsystem 606 prepares credit cards for customers. The statement subsystem 608 distributes credit card statements to customers.

The point-in-time processing area 602 and the subsystems 604, 606, 608 may reside on the application server 204 or other suitable computing device. The point-in-time processing area 602 accesses the rules database directly, without the need for an ETL process 506 (FIG. 5). In some embodiments, the point-in-time processing area 602 does not affect account attributes and operates only on data, such as account statement data files, that resulted from a prior batch process.

As an example of a point-in-time process, consider a customer initiating a new account with the client. The customer may have received a notice in the mail inviting the customer to apply by phone for a credit card account, such as the Premier account in the previous examples. The letters subsystem 604 may have participated in the generation of the notice. The customer may call a customer service representative who initiates a point-in-time process utilizing the embossing subsystem 606 to prepare a credit card with the customer's name and account number. The point-in-time processing area 602 extracts the data needed for account initiation, receives data from the customer service representative, and transmits information identifying the resulting actions to the embossing subsystem 606. Other examples of point-in-time processes are more fully explained in copending U.S. patent application Ser. No. 10/109,459, entitled, “System for Card Processing, Embossing & Fulfillment” (Attorney Docket No. 020375-003700) by Sharon K. Hogan, et al. filed on Mar. 26, 2002, and in copending U.S. patent application Ser. No. 10/108,806, entitled, “Method and Systems for Processing Card Reissue Transactions,” (Attorney Docket No. 020375-005000) by Rebecca Goodman, et al., filed on Mar. 26, 2002, and in copending U.S. patent application Ser. No. 10/108,217, entitled, “System for Ranking Card Reissue Transactions,” (Attorney Docket No. 020375-005100) by Jim K. Prendergast, et al., filed on Mar. 26, 2002, which applications are herein incorporated by reference in their entirety. These examples should not be considered limiting. Other examples might include a credit application process, wherein a customer may be requesting a higher credit limit.

Having described the processes for creating and using rules to process customer account and transaction data, attention is directed to FIG. 7 for a discussion of a process for simulating one or more rules during the rule creation process. FIG. 7 illustrates a simulation environment 700 having many of the same elements as the processing environment 500 of FIG. 5. As with the processing environment 500 of FIG. 5, the simulation environment 700 may reside on the application server 204 or other suitable computing environment. The simulation environment 700 includes a simulation area 704 having many of the engines discussed previously with respect to the processing area 504. Additionally, the simulation area 704 includes a simulation manager 706 that controls the simulation process and provides useful information relating to the sequence of activities in the simulation process, as will be explained in more detail hereinafter. The simulation environment also includes an interface 708 that provides information relating to the simulation process to a user, such as a client.

Using the simulation environment 700, clients may observe the effect of a particular rule on actual customer account and transaction data. A business rule to be simulated is loaded from the rules database 202 into the simulation area 704. The simulation manager 706 controls a step-by-step processing sequence based on the rule being simulated. As will be explained further below with reference to FIGS. 8A and 8B, the calculations, data calls, attribute updates, logical results, and the like, are presented to the user. Thus, the user is able to debug, modify, and optimize rules being incorporated into a policy.

In order to provide a high degree of realism, the simulation environment 700 may use real customer account and transaction data to perform the simulations. In some embodiments, users may request specific data sets. In other embodiments, the simulation environment 700 uses particular default data, such as “yesterday's data.” Data is accessed by the engines through each engine's data access layer 519. Some embodiments of the present invention allow users to select either multiple customer accounts for simulation purposes or a single, specified customer account.

In some embodiments of the present invention, such as the simulation environment 700 shown in FIG. 7, the simulation area 704 does not include a put engine 516. That is because the put engine 516 updates account attributes in response to business rules. However, during simulation, it is desirable to not update account attributes. Rather, information is provided to the user via the interface 708 that tells the user what is happening or what has happened during the simulation.

Attention is directed to FIG. 8A, which illustrates a first simulation screen display 800 in one non-limiting example of the present invention. The screen display 800 includes a rules window 802 that displays the rule hierarchy as previously discussed. In the rules window, a user may select a particular rule for simulation. The screen display 800 also includes a simulation window 804 that displays information relating to the rule being simulated. A user may specify a particular customer's account upon which to base the simulation by entering the account in the account field 806. A decision elements table 808 lists the elements, account attributes, and formula results relating to the rule being simulated.

Attention is directed to FIG. 8B, which illustrates a second screen display 810 in a simulation process. In a results window 812, a user is able to observe the results of the logical statements relating to the rule. Thus, in this example, the user is able to observe the results of the logical statements for the “$10 fee no waiver” rule discussed previously with respect to FIG. 1. The first logical statement 814 results in a false condition, while the second logical statement 816 results in a true condition based on the data for the account upon which the simulation is based. Because the first and second logical statements 814, 816 are joined by an “and” conjunction, the result of the rule is false, meaning that the action is not taken, as can be seen from the action statement 818. This is but one example of the simulation process of the present invention, and many other examples are possible and evident, in light of the disclosure herein, to those having skill in the art. Therefore, this example is not to be considered limiting.

Embodiments of the present invention are particularly useful in post-issuance account management environments. A number of customer service matters in a post-issuance environment are extremely labor intensive. For example, when a customer initiates a transaction that exceeds his credit limit, the customer typically contacts a customer service representative to request a credit limit increase. The customer service representative might review the customer's account history, check his credit score, evaluate other credit card programs that might be more appropriate for the customer given his spending habits, and the like, all of which typically requires human labor. Embodiments of the present invention may eliminate some or all of this human labor.

In one example, embodiments of the present invention may include customer-defined rules that evaluate a pool of accounts for those approaching or that have exceeded their respective credit limits. The range below and/or above the credit limit may be specifically defined by the customer. Once identified, the associated account history of each account may be evaluated against a number of criteria. For example, those accounts for which no late payments have been received may be candidates for credit limit increases. Rules may define a threshold number of late payments and a specific timeframe. Additional rules may trigger requests for credit scores. Those having scores within an acceptable range also may be candidates for credit limit increases. Based on the evaluations, a variety of actions may be taken.

Continuing with the example, accounts that qualify for credit limit increases may have the credit limit increased automatically. A letter, email, phone call, or the like, may be directed to the customer, all without human intervention, informing the customer of the credit limit increase. For those accounts that do not qualify for a credit limit increase, a communication to the customer may offer the customer a different credit card program, a bill consolidation program, a home equity line of credit, and/or the like. Thus, this simple example may substantially reduce the labor requirements for managing an existing presentation instrument account. Many other example are possible.

Other embodiments may review accounts for collection issues, security matters, fraud issues, reward programs, fee matters, offers, and the like. In some embodiments, rules are crafted such that all accounts in a pool of accounts are continuously monitored. In some embodiments, accounts are added to a target file for evaluation at predetermined dates/times or according to a predetermined schedule. Rules may operate on data from sources internal to the processor or external to the processor. For example, data for rule evaluation may come from merchants, clients, external databases, such as credit reporting databases, and the like. Many other examples are possible and apparent to those skilled in the art in light of this disclosure.

Having described embodiments of the invention generally, attention is directed to FIG. 9, which illustrates a exemplary method 900 of managing accounts in a post-issuance environment according to embodiments of the invention. The method 900 may be embodied in the system 200 of FIG. 2 or other appropriate system. Those skilled in the art will appreciate that the method 900 is merely exemplary of a number of possible methods according to embodiments of the invention. For example, other exemplary embodiments may include more, fewer, or different steps than those illustrates and described here. Further, the steps illustrated and described here may be traversed in different orders than shown here.

The exemplary method 900 begins at block 902, at which point one or more accounts are established. The accounts may be established according to the teachings herein, although this is not a requirement. As is apparent to those skilled in the art, new accounts may be continually added to and/or removed from a pool of monitored accounts.

At block 904, rules are received for managing accounts. The rules may be selected from a menu of pre-defined rules, may be uniquely defined, or the like, according to the teachings herein. The rules may define events and/or triggers, conditions, and actions to be taken, as described above.

At block 906, accounts are monitored according to the rules. In some embodiments, this includes adding accounts to a trigger file, as is shown by block 908. In some embodiments, this includes segmenting accounts by grouping accounts that satisfy a condition 910. Accounts that have been added to a trigger file at block 908 also may be segmented at block 910, according to conditions upon occurrence of the trigger event.

Segmented accounts for which a condition has been satisfied may, at block 912, have an action taken relating to the account. The action may be to send correspondence, annotate the account, change an operating parameter of the account, request additional data relating to the account, or the like. Thereafter, accounts may continue to be monitored at block 906. Those skilled in the art will appreciate a variety of interactions among the blocks other than those illustrated and described here.

Having generally described a method of managing accounts according to embodiments of the invention, a specific example follows relating to a number of rules for managing a credit card account having a rewards program associated therewith. In this specific example, the following terms and conditions relate to the account and the program:

-   -   New credit card accounts qualify for the program and receive         5000 bonus points;     -   If a new card is not used within the first thirty days following         creation of the account, the card holder forfeits the 5000         points;     -   If the new card is not used in the first thirty days following         creation of the account, then the cardholder is billed an annual         fee of $50 for the card.

The following rules are established for monitoring new accounts relating to the program. The first identifies the account as one that qualifies for the reward program. The second monitors all cards for compliance with the terms and conditions relating to the reward program:

Rule 1:

Event: Card_Issuance;

Condition: If Account_Creation_Data=Today's_Date;

Action: Place account in Rewards_Trigger_File;

-   -   Add 5000 Bonus Points to Account.         Rule 2:

Event: Daily_Account_Cycle;

Rule: If Account_Creation_Data+30=Today's_Date AND Inactivity_Flag=Y;

Action: Post Annual Fee to Account;

-   -   Send Inactivity Letter to Cardholder;     -   Adjust Bonus Point Balance.

Thus, when a card is created for the customer, 5000 points is added to the customer's account, and the account is added to a Rewards Program trigger file for ongoing monitoring. For example, purchases using the card result in reward points. If the card is not used in the first thirty days, the bonus is subtracted from the account, a letter is sent to the customer, and the annual fee is posted to the account. Those skilled in the art will appreciate the foregoing specific example is merely exemplary of basic rules that may be created with respect to managing accounts. Others also may be created and, like those in this specific example, result in labor savings for managing existing accounts.

FIG. 10 illustrates an exemplary specific embodiment of an account management process 1000 that employs a number of features described herein. Those skilled in the art will appreciate that the process 1000 is merely exemplary of a number of possible processes according to embodiments of the invention. It should also be appreciated that all steps of the process 1000 need not be traversed each time the process occurs. Other exemplary processes according to other embodiments may include more, fewer, or different steps than those illustrated herein.

The process 1000 begins at block 1002 at which a client establishes an account for the purposes of processing its cardholder accounts. At block 1004, the client selects, creates, or otherwise defines rules for processing its cardholder accounts. This may be accomplished, for example, using the client interface depicted in the screen display 100 of FIG. 1. The rules include at least first and second rules, each having a unique event associated therewith. At least one of the first and second events is a client-defined event. That is, at least one of the events is not pre-defined by the processor.

At block 1006, account monitoring begins. During account monitoring, client cardholder accounts are monitored for the occurrence of an event. According to block 1006, the accounts are monitored for the occurrence of the first event, although the accounts could be monitored for any event in any applicable rules, including client-defined events.

At block 1008, the occurrence of the first event is detected and the associated rule is evaluated as described herein. In response to the evaluation, any of a variety of actions may be taken at block 1010. Additionally, however, information may be written to one or more files at block 1012. For example, a first client data file may be opened and appropriate information written to it. The file may be closed and another file opened and information written to it. This may continue throughout evaluation of the rule. Moreover, account level criteria may be set during evaluation of the rule. This takes place at block 1014. The account level criteria may be made available during evaluation of other rules upon the occurrence of other events.

At block 1016, the account may be segmented at previously described.

At block 1018, the clients accounts are again monitored, this time for the occurrence of another event, in this case the second event. At block 1020, upon the occurrence of the second event, the rule associated with the second event is evaluated and appropriate actions are taken at block 1022. Actions taken in response to or during evaluation of the second rule may include writing information to multiple files in addition to the actions discussed previously herein. Moreover, rule evaluations and actions taken relating to the second rule may include using the account level criteria set at block 1014. Many other possibilities exist.

Having described several embodiments, it will be recognized by those of skill in the art that various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the invention. Additionally, a number of well known processes and elements have not been described in order to avoid unnecessarily obscuring the present invention. For example, those skilled in the art know how to arrange computers into a network and enable communication among the computers. Additionally, those skilled in the art will realize that the present invention is not limited to post-issuance management of presentation instrument accounts. For example, the present invention may be used to manage accounts relating to utility bills, phone bills, mortgages, brokerage accounts, and the like. Accordingly, the above description should not be taken as limiting the scope of the invention, which is defined in the following claims. 

1. A method of managing one or more presentation instrument accounts, comprising: receiving at a host computer system information from a client defining an account management rule, wherein the rule comprises: a client-defined event; a condition; and an action to be taken if the condition is satisfied upon the occurrence of the client-defined event; at the host computer system, monitoring the one or more presentation instrument accounts for the occurrence of the client-defined event; at the host computer system, upon the occurrence of the client-defined event for a specific account, evaluating the account management rule; based on the evaluation, taking the action, thereby managing the account without human intervention; and providing notification of the action to an individual.
 2. The method of claim 1, wherein taking the action comprises: opening each of a plurality of files; writing information to each of the plurality of files; closing each of the plurality of files; continuing to evaluate the account management rule; opening at least one additional file; and writing information to the at least one additional file.
 3. The method of claim 1, wherein the client-defined event comprises a first event, wherein the account management rule comprises a first account management rule, and wherein the action includes setting an account level criteria, the method further comprising: monitoring the one or more presentation instrument accounts for the occurrence of a second event relating to a second account management rule; and using the account level criteria, at least in part, to evaluate the second account management rule.
 4. The method of claim 1, wherein the condition comprises a logical expression using at least one element.
 5. The method of claim 4, wherein the at least one element is derived from one or more account attributes.
 6. The method of claim 5, wherein the one or more account attributes are selected from a group consisting of activity flag, account creation data, credit balance, and rewards program balance.
 7. The method of claim 1, wherein the action results in a change to an account attribute.
 8. The method of claim 1, wherein the account management rule is selected from a library of account management rules.
 9. A computer-readable medium having computer-executable instructions for performing a method of managing one or more presentation instrument accounts, the method comprising: receiving information from a client defining an account management rule, wherein the rule comprises: a client-defined event; a condition; and an action to be taken if the condition is satisfied upon the occurrence of the event; monitoring the one or more presentation instrument accounts for the occurrence of the client-defined event; upon the occurrence of the event for a specific account, evaluating the condition; and based on the evaluation, taking the action, thereby managing the account without human intervention.
 10. The method of claim 9, wherein taking the action comprises: opening each of a plurality of files; writing information to each of the plurality of files; closing each of the plurality of files; continuing to evaluate the account management rule; opening at least one additional file; and writing information to the at least one additional file.
 11. The computer-readable medium of claim 9, wherein the client-defined event comprises a first event, wherein the account management rule comprises a first account management rule, and wherein the action includes setting an account level criteria, the method further comprising: monitoring the one or more presentation instrument accounts for the occurrence of a second event relating to a second account management rule; and using the account level criteria, at least in part, to evaluate the second account management rule.
 12. The computer-readable medium of claim 9, wherein the computer-executable instructions further include instructions for: collecting bankcard transaction data; and processing the bankcard transaction data using the account management rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition.
 13. The computer-readable medium of claim 9, wherein receiving information identifying a condition comprises receiving a logical expression using at least one element.
 14. The computer-readable medium of claim 13, wherein the at least one element is derived from one or more account attributes.
 15. A system for managing one or more presentation instrument accounts, comprising: a processor; a storage device; an output device; wherein the processor is configured to: receive from a client a client-defined event; receive information identifying a condition relating to at least one element associated with bankcard accounts; receive information defining an action to be taken based on the condition upon the occurrence of the event; and store the event, the condition, and the action as an account management rule.
 16. The system of claim 15, wherein the processor is further configured to: collect bankcard transaction data; and process the bankcard transaction data using the account management rule such that, upon the occurrence of the event, the action is taken with respect to bankcard accounts that satisfy the condition.
 17. The system of claim 15, wherein in processing the bankcard transaction data, the processor is further configured to: open each of a plurality of files; write information to each of the plurality of files; close each of the plurality of files; continue to process the bankcard transaction data using the account management rule; open at least one additional file; and write information to the at least one additional file.
 18. The system of claim 15, wherein the client-defined event comprises a first event, wherein the account management rule comprises a first account management rule, wherein the action includes setting an account level criteria, and wherein in processing the bankcard transaction data, the processor is further configured to: monitor the one or more presentation instrument accounts for the occurrence of a second event relating to a second account management rule; and use the account level criteria, at least in part, to evaluate the second account management rule.
 19. The system of claim 15, wherein the information identifying a condition comprises a logical expression using at least one element.
 20. The system of claim 19, wherein the at least one element is derived from one or more account attributes. 